Removes 94 Meteor method registrations that had no callers anywhere in
the repository — they were marked for removal in 9.0.0 by the
deprecation logging shipped earlier on develop. Files that ended up
containing only imports and declare-module blocks after the removal
were deleted, and matching side-effect imports were stripped from
sibling index.ts barrels.

The removal keeps a skip-list of methods that are still reachable
indirectly: admin settings buttons that dispatch via useMethod(value)
in MethodActionInput.tsx, and a handful of cloud:* methods invoked from
admin actions. Those will be revisited once their callers move to REST.

Removed by scripts/remove-orphan-ddp-methods.mjs +
scripts/cleanup-after-orphan-removal.mjs from docs/ddp-audit.json.

BREAKING CHANGE: 94 DDP methods previously registered are no longer
callable. Any DDP-only client that still relies on Meteor.call(<name>)
for these methods must migrate to the corresponding REST endpoint
(see docs/ddp-audit.md for the mapping) or, where no REST equivalent
exists, drop usage.

The first pass of the orphan removal triggered three classes of CI
failures:

1. `@typescript-eslint/no-unused-vars` errors where the import-pruner
   removed type imports that were still referenced inside the
   `declare module '@rocket.chat/ddp-client' { interface ServerMethods
   { ... } }` augmentation blocks. The pruner was stripping declare
   module content before checking name usage, so types like
   `IImport`, `ICreatedRoom`, `IMessageSearchProvider`,
   `RoomType`, `RocketChatRecordDeleted`, and `WithId` were
   incorrectly marked unused.

2. `@typescript-eslint/no-unused-vars` errors where the interface
   ServerMethods entries for the removed methods were still pointing
   at types we had already imported. The new
   scripts/strip-orphan-interface-entries.mjs walks each declare
   module block in step with the removal plan and drops the matching
   interface entries (and the whole declare module block if it
   becomes empty), keeping the implementation removal and the type
   surface in sync. A skip-list inside the script restores entries
   for the 8 methods that turned out to have callers we missed.

3. `error TS2345: Argument of type '...' is not assignable to
   parameter of type 'keyof ServerMethods'` for methods that the
   audit reported as orphan but were called through dynamic dispatch
   the literal-string scanner couldn't see:

     - `permissions/get`, `rooms/get`, `subscriptions/get`,
       `public-settings/get`, `private-settings/get` are called
       via a template literal in
       apps/meteor/client/lib/cachedStores/CachedStore.ts as
       `sdk.call(\`${this.name}/get\`)`.
     - `samlLogout` is called via `sdk\n.call('samlLogout', ...)`
       in apps/meteor/client/meteor/login/saml.ts — the audit's
       `\bsdk\.` regex didn't tolerate whitespace between
       `sdk` and `.call`.
     - `blockUser` and `unblockUser` are called via a conditional
       `useMethod(isUserBlocked ? 'unblockUser' : 'blockUser')` in
       apps/meteor/client/views/room/hooks/useUserInfoActions/actions/useBlockUserAction.ts,
       which the scanner can't reach.

   Restoring those 8 implementations and adjusting the matching barrel
   imports puts the runtime contract back together. The scripts'
   detection patterns will be hardened in a follow-up.

Also drops apps/meteor/app/push/server/methods.ts and its
`import './methods'` from `apps/meteor/app/push/server/index.ts`:
the file's last DDP entry was removed in an earlier pass, leaving the
file with nothing but an unused `PushUpdateOptions` alias and an
orphan interface declaration.

apps/meteor/server/importPackages.ts:71 imports
../app/meteor-accounts-saml/server, so the directory needs an index.ts
that loads the side-effect modules. The previous cleanup pass deleted
the barrel when it looked dead, breaking lint and the runtime require.

Lists the 87 Meteor (DDP) methods this PR removes, with the
matching REST endpoint where one exists. Major bump on
@rocket.chat/meteor flags the breaking-change semantics for
external DDP/SDK clients.

The tagged describe blocks in tests/end-to-end/api/methods.ts that
exercised method.call/:method directly against the removed methods
no longer have anything to test - the implementations are gone in
this PR. Removed the four blocks (1005 lines):

  - [@cleanRoomHistory]
  - [@getUsersOfRoom]
  - [@updateMessage]
  - [@setUserActiveStatus]

Two unrelated test files used `saveUserPreferences` as a setup step
before exercising a different feature. Migrated those callsites to
POST /v1/users.setPreferences so the test still does what it intended
once the DDP method is gone:

  - tests/end-to-end/api/direct-message.ts: setting emailNotificationMode
    before creating a DM.
  - tests/end-to-end/api/teams.ts: setting emailNotificationMode before
    inviting the user to a team.

The `methodCall` import in direct-message.ts was the only remaining
reference; dropped it to satisfy the unused-vars rule.

UI tests cover the forgot-password flow which triggers
`sendForgotPasswordEmail` through Meteor's `Accounts.forgotPassword`
client API — the call chain is invisible to the audit's static
string-literal scan.

Restores the method file from origin/release-9.0.0, drops the entry
from the changeset (count 87 -> 86), and adds it to the NEVER_REMOVE
skip list in scripts/remove-orphan-ddp-methods.mjs alongside the
other dynamic-dispatch survivors so a future audit run doesn't try
to remove it again.

The [@getReadReceipts] EE test used readMessages as a fixture step to
simulate the invited user reading the main room before checking that
both sender and recipient receipts show up. readMessages is removed
in this PR; the test now POSTs /v1/subscriptions.read instead, which
is the supported REST equivalent.